ci: setup pkg.pr.new #271
Merged
ci: setup pkg.pr.new #271
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
AriPerkkio
commented
Aug 21, 2024
|
Verified the same script in separate repo: AriPerkkio/eslint-remote-tester#549 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
maintrigger an automatic release/pkg-pr-newin a PRThis will make testing PRs like #270 a lot easier. In that PR we need to verify that packages are resolved correctly in real environments. Testing such changes by linking packages with
file://orlink://protocols inpackage.jsondoesn't provide good confidence - using real published packages is better.I've used the workflow from Vite as reference: https://github.com/vitejs/vite/blob/main/.github/workflows/publish-commit.yml